Subject: Transport IDs

From: [email-masked] (Erickson, Rodger)
Date: Thu, 22 Feb 1996 16:45:33 -0800

RFC1795 contains a contradiction on page 14 that I would like to get 
some comments on from those who have implemented the spec.  The paragraph on 
Transport ID fields says that they are learned during the Capabilities 
Exchange and should not be varied after the Capabilities Exchange is 
completed.  In the very next paragraph it says that the Target Transport Id 
(along with the Target Data Link Correlator and Target Port ID) must not 
vary after the ICANREACH_CS and furthermore that the origin DLSw must allow 
these fields to vary until the ICANREACH_CS.  Similar points are then made 
for the Origin Transport ID (it can vary until REACH_ACK).

     What about this?  We can't have the Transport IDs not changing after 
the Capabilities Exchange *AND* varying up until either the ICANREACH_CS or 
REACH_ACK.

     Cisco allows this value to vary after the Capabilities Exchange.  How 
have other implementers handled this contradiction?

     Thanks!

     Rodger Erickson
     Wall Data